We encountered a case just before upgrading from 9.2.0.4 to 9.2.0.5, where a user edited an object and linked it in shareable edit mode, and somewhere within the editing of other requirements he noticed that the object had gone missing (he thought maybe he accidentally pressed delete button or something like that). He unlocked section without saving, and object became visible again. Then he continued to edit and saved. Next time he looked for the object, it was gone.
History Check utility does show history mismatch against this object, since there is no info of it being purged but it does not exist in the module anymore. Last history record on module level shows editing and linking. No cutting or deletion even near the section where requirement was located.
Our workaround was that author created a new object with same data, but ofcourse we lost the old ID number which is not very nice since it was an old requirement and existed already in previous baselines...
I hope this was something in just 9.2.0.4 (with the other shareable edit bug that made possible to create duplicate absolute numbers), but I am a bit worried if there still could be a scenario in shareable edit usage where a requirement can be lost without a trace...
SystemAdmin - Wed Sep 29 14:14:00 EDT 2010 |